Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(gatsby): fix incorrect intersection of filtered results (#30594) #30619

Merged
merged 1 commit into from
Apr 1, 2021

Conversation

gatsbybot
Copy link
Collaborator

Backporting #30594 to the 2.32 release branch

(cherry picked from commit e432c23)

@gatsbot gatsbot bot added the status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer label Apr 1, 2021
@pieh pieh removed the status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer label Apr 1, 2021
@pieh pieh force-pushed the backport-2.32-30594 branch 3 times, most recently from e968283 to 0e7dc96 Compare April 1, 2021 18:18
* add failing test

* actually failing test

* make test independent of other tests

* add invariant for filter intersection assumptions

* add failing integration test

* fix test 🤦‍

* actually fix this heisenbug

* update redux state snapshot

* perf: mutate status state directly

Co-authored-by: Michal Piechowiak <[email protected]>

* only newly created nodes should get a counter

* tweak comment

Co-authored-by: Michal Piechowiak <[email protected]>

Co-authored-by: Michal Piechowiak <[email protected]>
(cherry picked from commit e432c23)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants